[release/5.0] Avoid including the validation stage if not necessary (#6376)#6467
Merged
mmitche merged 1 commit intodotnet:release/5.0from Oct 27, 2020
Merged
Conversation
This removes the Validation stage if both of these conditions are false: - There's an inline v2 publishing (for checking whether a channel exists) - Any post-build validation is enabled Every job dependency transition has a pretty decent cost. The stage typically takes a minute or so, and also requires getting a machine, etc. This adds up
riarenas
approved these changes
Oct 27, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This removes the Validation stage if both of these conditions are false:
Every job dependency transition has a pretty decent cost. The stage typically takes a minute or so, and also requires getting a machine, etc. This adds up
Customer Impact
Build times stay the same
Regression
No
Risk
Low. Been working master for quite a while
Workarounds
None